home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: MAUS
- Date: Tue, 31 May 94 14:27:50 +0100
- From: sjg
- X-Mts: smtp
-
-
- > Anyway, menu shortcuts SHOULD be configurable from an application, so
- > the user can throw away control A altogether. I think we should also be
- > thinking of developing guidelines for such a configurable menu assignment.
- > A few ideas:
-
- Menu shortcuts ought to be configurable, and even if not, they ought to be
- read dynamically from the resource. So if a user changes the ^A in the the
- file to ^P (why ?) he then gets to use ^P as the key for the menu entry.
-
- This is pretty simple to do, but it would be simpler still if there was a
- library function :-) A function that scans the strings then returns a pointer
- to array of longs (words?) that describe the value given by the AES on a
- key event would do. If ^A (now ^P) was on the 15th menu entry, then menuKey[15]
- would be the AES's value for ^P.
-
- At least this way, RSC editors can change the strings into a new language, and
- give meaningful shortcuts to the user (for other than the 'standard' ones, of
- course :-)
-
- Simon.
-
-
-